PART 3 – Editing the Code
The last part of this project involves editing the code of the generated ABAP/4 BDC program. This program needs to upload the files the legacy programmer has provided you, as well as code any special logic. To finish the program, you will need to create an internal table that will store all the values that need to be populated in the Vendor Master Data table (LFA1). You will need to setup a Parameters statement to accept the import files. Finally, you will need to write special logic to get the desired output.
- If the BDC program is not currently open, go to the ABAP Workbench and open the BDC program. After the reports statement, use the tables statement to call two tables:
|
Table |
Description |
|
LFA1 |
Vendor Master Data |
|
RLGRAP |
Structure used when uploading/downloading file formats |
- Next, use the parameters statement to accept the input of the text file (path):
parameters: p_file like rlgrap-filename.
- Create an internal table that contains the structure of the import file.
data: begin of itab occurs 10,
vendor like lfa1-lifnr,
name like lfa1-name1,
city like lfa1-ort01,
zip like lfa1-pstlz,
end of itab.
- Note: make sure you use the data dictionary to become familiar with the LFA1 table and its fields.
- Review the text files that will be used for the upload. Notice the space that is separating each value. To account for the space in the import file, use the following variables (data object):
data: wf_record(80),
wf_split type x value '09'. "this represents a tab in a file
- Question: what do you think ‘bdcrecxx’ is referring to from your code?
- After the ‘Start-of-Selection’ statement, place a new subroutine that gets the data from the input file:
perform get_data.
- Tip: you can double-click on the get_data name and ABAP/4 will automatically generate the required entries in your code to initialize the subroutine.
- After the form ‘get_data’ statement, use the open dataset command to get the text file:
open dataset p_file in text mode.
- Review the following Do Statement (we will go over this command in lecture).
do.
read dataset p_file into wf_record.
if sy-subrc ne 0.
exit.
else.
split wf_record at wf_split into itab-vendor itab-name itab-city
itab-zip.
append itab.
endif.
enddo.
- The last statement in your program (before ‘endform.’) should be:
close dataset p_file.
- After the open_group statement, start looping your program.
loop at itab. "start looping through all all records from file
- Use the table below to replace the BDC Field values with the values from the internal table:
|
BDC Field Name |
Original Value |
Change to Value |
|
RF02K-LIFNR |
ZBDCTESTXX |
itab-vendor. |
|
BDC_CURSOR |
RF02K-KTOKK |
Refer to If statement below |
|
LFA1-NAME1 |
BDC Test Borquez XX |
itab-name. |
|
LFA1-SORTL |
BDCTE |
itab-name+0(5). |
|
LFA1-ORT01 |
Beverly Hills |
itab-city. |
|
LFA1-PSTLZ |
90211 |
itab-zip. |
- To determine the type of group, use the following if statement:
if itab-vendor = space.
perform bdc_field using 'RF02K-KTOKK'
'kred'.
else.
perform bdc_field using 'RF02K-KTOKK'
'LIEF'.
endif.
- After the statement:
perform bdc_transaction using 'MK01'.
- Refresh the data with the command:
refresh bdcdata. " clear all records in table, not just header record
- Press F8 or Execute to run the program:
- When your program runs, use the following parameters (make sure you check the Keep Session check box):
- Click on Execute.
If you are successful with executing the program, you could expect the following screen:
- Test the results of your program by going to transaction SM35.
- If you forget the name of your session, click on the overview button. You should be able to see your session in the ‘Session still to be processed’ area.
- Double-click on your session:
- Click on Process.
The system will now walk you through the batch process for your text file. Notice the values that are given to each field during this walk through. In the future, you may run this process in ‘Background’ mode if you are importing thousands of records, rather than just a few. This is a good test to see if your program can successfully run the text file.
When the batch process completes, you will see the following window:
- To check the log, go back to SM35 and click overview. Select your session and click on Log from the toolbar.
You will see the results from your successful batch input:
That’s all folks!
 |
 |
